Repository navigation
Update CHROMIUM.md - #1944
Update CHROMIUM.md#1944
Conversation
Fix build instructions: - It is required to run again gclient sync after switching to the wolvic branch. Otherwise, the gen gen command fails. - autoninja doesn't work anymore to build the project. Directly calling ninja allows to build without issues.
svillar
left a comment
There was a problem hiding this comment.
Thanks!
I just have one comment
|
|
||
| ``` | ||
| autoninja -C out/Default content_aar ui_aar | ||
| ninja -C out/Default content_aar ui_aar |
There was a problem hiding this comment.
I still use autoninja without any issue
There was a problem hiding this comment.
OK, thanks for you feedback. On my side, I couldn't make it work despite multiple trials. Should I suggest to fall back on ninja if autoninja doesn't work?
There was a problem hiding this comment.
I updated this part, is that better?
|
Also encountered this issue. Using ninja allows compilation to pass, but autoninja fails to compile successfully. Additionally, I have another question: I also tried building with the wolvic-chromium/release/1.2.x branch of the wolvic-chromium repository and the v1.2.3-chromium version of the wolvic repository, but the v8 deserializer error still occurs during runtime. It seems the issue might be caused by a mismatch between the compiled outputs of the two repositories? I’d like to ask if there is any documentation specifying which commit of wolvic-chromium corresponds to the released versions of the wolvic repository? |
I found that using the in-tree autoninja is much more reliable than the top of the tree version from depot_tools. There is a depot_tools checkout inside the chromium repos that should work fine for any checkout you have.
Not sure if it's the same issue but currently we cannot use minification when creating the packages because there are crashes here and there, and also some of the code we require for example for YouTube seems to be removed from the final package.
We're using a branch called wolvic |
Fix build instructions:
gn gencommand fails.autoninjadoesn't work anymore to build the project. Directly callingninjaallows to build without issues.The second issue is probably due to an incompatibility between an up-to-date
depot_toolsand thewolvicbranch of Chromium.